
%%%%%%%%%%%%%%%%%%%%%%% file typeinst.tex %%%%%%%%%%%%%%%%%%%%%%%%%
%
% This is the LaTeX source for the instructions to authors using
% the LaTeX document class 'llncs.cls' for contributions to
% the Lecture Notes in Computer Sciences series.
% http://www.springer.com/lncs       Springer Heidelberg 2006/05/04
%
% It may be used as a template for your own input - copy it
% to a new file with a new name and use it as the basis
% for your article.
%
% NB: the document class 'llncs' has its own and detailed documentation, see
% ftp://ftp.springer.de/data/pubftp/pub/tex/latex/llncs/latex2e/llncsdoc.pdf
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


\documentclass[runningheads]{llncs}

\usepackage{amssymb}
\setcounter{tocdepth}{3}
\usepackage{graphicx}

\usepackage{url}
\urldef{\mailsa}\path|{alfred.hofmann,ursula.barth,ingrid.beyer,natalie.brecht,|
\urldef{\mailsb}\path|christine.guenther,frank.holzwarth,piamaria.karbach,|
\urldef{\mailsc}\path|anna.kramer,erika.siebert-cole,lncs}@springer.com|
\newcommand{\keywords}[1]{\par\addvspace\baselineskip
\noindent\keywordname\enspace\ignorespaces#1}

\begin{document}

\mainmatter  % start of an individual contribution

% first the title is needed
\title{Representing Legacy Systems as MOF Models}

% a short form should be given in case it is too long for the running head
\titlerunning{Representing Legacy Systems as MOF Models}

% the name(s) of the author(s) follow(s) next
%
% NB: Chinese authors should write their first names(s) in front of
% their surnames. This ensures that the names appear correctly in
% the running heads and the author index.
%
\author{Alfred Hofmann%
\thanks{Please note that the LNCS Editorial assumes that all authors have used
the western naming convention, with given names preceding surnames. This determines
the structure of the names in the running heads and the author index.}%
\and Ursula Barth\and Ingrid Beyer\and Natalie Brecht\and\\
Christine G\"{u}nther\and Frank Holzwarth\and Pia Maria Karbach \and\\
Anna Kramer\and Erika
Siebert-Cole}
%
\authorrunning{Hui Song}
% (feature abused for this document to repeat the title also on left hand pages)

% the affiliations are given next; don't give your e-mail address
% unless you accept that it will be published
\institute{Springer-Verlag, Computer Science Editorial,\\
Tiergartenstr. 17, 69121 Heidelberg, Germany\\
\mailsa\\
\mailsb\\
\mailsc\\
\url{http://www.springer.com/lncs}}

%
% NB: a more complex sample for affiliations and the mapping to the
% corresponding authors can be found in the file "llncs.dem"
% (search for the string "\mainmatter" where a contribution starts).
% "llncs.dem" accompanies the document class "llncs.cls".
%

\toctitle{Lecture Notes in Computer Science}
\tocauthor{Authors' Instructions}
\maketitle


\begin{abstract}
The abstract should summarize the contents of the paper and should
contain at least 70 and at most 150 words. It should be written using the
\emph{abstract} environment.
\keywords{We would like to encourage you to list your keywords within
the abstract section}
\end{abstract}


\section{Introduction}

Nowadays, software systems are usually running on complex environments, severing for various users. To keep on adapting to the changes of environments and the new requirements from users, we often need to \emph{manage} these systems. This management work is not easy because systems are very complex. Currently, model-driven technologies are widely accepted for handling complex data, and thus it is a natural thought to employ such technologies for managing systems. For example, we can use model transformation technologies like QVT \cite{OMG}or ATL to abstract the system states into a high level view for better understanding, or to maintain the relation between two heterogeneous systems, we can also use model validation technologies like QCL to automatically monitor some system properties when the systems are still running. Since most of these model-driven technologies are based on MOF standard, the first step towards this dream is to represent the system states as MOF \cite{OMG} models, either static states like code structures or dynamic states like runtime configuration and statistic. Currently, many systems are not developed strictly according to the model-driven approach, and such legacy systems do not have existing MOF models as representations.



MoDisco project proposes a common approach to represent legacy systems as models, as shown in Figure

\bibliographystyle{splncs}
\bibliography{reference}

\subsection{The section}
\end{document}
